Decoupling and relocating bookmarks and annotations from files

ABSTRACT

Disclosed are various examples for generating, storing, and loading drawings separate from a file. A request can be received to generate a drawing in a file. A data object can be generated corresponding to the drawing. The data object can include characteristics of the file proximate to an area in the file associated with the drawing. The data object can be stored in a data store associated with the file. A request can be received to open the file. The file can be loaded from the data store. The position of the drawing within the file can be determined based on a stored data object. The file can be rendered including the drawing at the determined position.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/002,293, entitled “Decoupling and Relocating Bookmarks andAnnotations from Files,” filed Jun. 7, 2018, which is a continuation ofU.S. Pat. No. 9,996,514, entitled “Decoupling and Relocating Bookmarksand Annotations from Files,” issued Jun. 12, 2018, each of which arehereby incorporated by reference.

BACKGROUND

When working in a file, a reference can be created and stored within thefile. In one example, pilots can create references in files related toupcoming travel assignments. When circumstances change, such as theweather, the pilot can receive new versions of the files. However, thereferences in the prior version of the file are stored within the file.When a pilot receives a new version of the file from a computingenvironment, the new version of the file omits any references added inthe earlier version that is locally stored in a client device of thepilot.

Another user can modify text in the file that corresponds to a referencecreated by the pilot. Because the reference is stored on a client deviceof the pilot within the file, the other user is unaware that the pilotcreated a reference for the text being modified. The pilot can receivean updated version of the file omitting text corresponding to areference the pilot generated the earlier version of the file.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the present disclosure can be better understood withreference to the following drawings. The components in the drawings arenot necessarily to scale, with emphasis instead being placed uponclearly illustrating the principles of the disclosure. Moreover, in thedrawings, like reference numerals designate corresponding partsthroughout the several views.

FIG. 1 is a drawing of a networked environment according to variousexamples of the present disclosure.

FIGS. 2-4 are pictorial diagrams of example user interfaces rendered bya client in the networked environment of FIG. 1 according to variousexamples of the present disclosure.

FIG. 5 is a sample data object corresponding to a reference according tovarious examples of the present disclosure.

FIGS. 6 and 7 are flowcharts illustrating examples of functionalityimplemented as portions of a file management application and a renderingapplication executed in a computing environment in the networkedenvironment of FIG. 1 according to various examples of the presentdisclosure.

DETAILED DESCRIPTION

The present disclosure relates to generating a reference for a file andstoring the reference decoupled from the file. According to one example,an airline employee creates a file related to an upcoming flight, suchas a flight manual document. The airline employee uploads the file to aserver. The server distributes the file to a client device associatedwith a pilot. The pilot reviews the file and creates notes, bookmarks,or other references for the file. The client device saves the referencesseparate from the file. When the pilot later reviews the files prior tothe flight, a rendering application places the references in the file.

Information about the flight can change before the scheduled flightoccurs. An airline employee can update the file to reflect any changesthat occur, which may cause the location of the references within thefile to change. The updated file can be uploaded to the computingenvironment and distributed to the client device. When the pilot opensthe updated file, the rendering application can place the referencesfrom the original file in the updated file. The pilot can review theupdated file without losing the references that the pilot added in theoriginal file.

In one example, a rendering application executing on a client devicereceives a request to generate a reference within a file. For example,the rendering application can allow a user to create a bookmark orreference within a file. When rendering the file on a display of theclient device, the rendering application can identify characteristics ofthe data object and can superimpose the references onto the rendering ofthe file based on the characteristics. That is, the characteristics ofthe data object can be used by the rendering application to determineone or more positions within the file where the references should besuperimposed. In one example, the characteristics are proximate to wherethe reference was created, such as the text strings preceding andsubsequent to the reference.

The rendering application can transmit the data object to a filemanagement application. The file management application can store thedata object in a data store. The data object can be stored separate fromthe file. The reference can be a bookmark, an annotation, or anothertype of reference. The characteristics of the file that are within thedata object can include an indication of whether the reference is abookmark, an annotation, or another type of reference. Thecharacteristics of the reference can also include a section, asubsection, an original page number, a page size, a text stringpreceding the area, a text string subsequent to the area, a referencetype, a location relative to an image, a name of the file, a versionnumber of the file, and other characteristics.

Another user can update the file using another client device, forexample, another user can make changes to a first version of a file. Theclient device can upload the updated file to a server. As an example, ifinformation in a file about a flight changes, an employee from theairline can update the file with the information that has changed. Thefile management application can receive the updated file from the serverand store the updated file in a data store, for example, as a secondversion of the file. The rendering application can receive a request toopen the updated file. The reference application can request the updatedfile from the file management application. The file managementapplication can load the updated file and data objects representingreferences associated with the file from the data store. In one example,the data objects correspond to a first version of the file. The filemanagement application can send the updated file and the data objects tothe rendering application. According to one example, the file managementapplication sends the second version of the file and data objectscorresponding to the first version of the file to the renderingapplication. The rendering application can determine a position in theupdated file to place each of the references based on the data objects.The rendering application can render the updated file along with thereferences.

According to one example, the rendering application can determine ifmore than one potential position to place a reference exists within anupdated file. If only one potential position exists within the updatedfile, the rendering application can place the reference at the potentialposition within the updated file. If more than one potential positionexists, the rendering application can generate a score for each of thepotential positions based on the data object associated with thereference. The rendering application can select one of the potentialpositions based on the scores.

When a request to open a file is received by the rendering application,the file management application can retrieve data objects correspondingto references from a data store. As an example, the file managementapplication can load the data objects by querying the data store andplacing the returned data objects into local memory. The file managementapplication can identify which of the references are associated with thefile. According to one example, the file management application queriesthe data store for all references with a unique identifier correspondingto the file. The rendering application can determine a position in thefile to place the references based on the characteristics associatedwith the data objects. The rendering application can render the fileincluding the references, such as by overlaying or superimposing thereferences onto the file when the file is rendered in a user interfaceon a display.

With reference to FIG. 1, shown is a networked environment 100 accordingto various examples. The networked environment 100 shown in FIG. 1includes a computing environment 103, a client device 106, andpotentially other components, which are in data communication with eachother over a network 109. The network 109 includes, for example, theInternet, intranets, extranets, wide area networks (WANs), local areanetworks (LANs), wired networks, wireless networks, other suitablenetworks, or any combination of two or more networks. The networks caninclude satellite networks, cable networks, Ethernet networks, telephonynetworks, or other types of networks.

The computing environment 103 can include, for example, a servercomputer or any other system providing computing capabilities.Alternatively, the computing environment 103 can employ multiplecomputing devices that may be arranged, for example, in server banks,computer banks, or other arrangements. The computing devices can belocated in a single installation or may be distributed among manydifferent geographical locations. For example, the computing environment103 can include multiple computing devices that together form a hostedcomputing resource, a grid computing resource, and any other distributedcomputing arrangement.

In some cases, the computing environment 103 operates as at least aportion of an elastic computing resource where the allotted capacity ofprocessing, network, storage, or other computing-related resources mayvary over time. The computing environment 103 can also include or beoperated as virtualized computer instances that are executed in order toperform the functionality that is described herein. Generally, thecomputing environment 103 can be operated in accordance with particularsecurity protocols such that it is considered a trusted computingenvironment.

Various systems can be executed in the computing environment 103. Also,various data is stored in a data store 112 that is accessible to thecomputing environment 103. The data store 112 shown in FIG. 1 can berepresentative of multiple data stores 112. The data stored in the datastore 112 is associated with the operation of the various componentsdescribed below.

A management service 115 and other services can be executed in thecomputing environment 103. The management service 115 can manage andoversee the operation of one or more client devices 106. The managementservice 115 can manage access to the files 121 and the references 124from various client devices 106. That is, the management service 115 candetermine whether a user, a device, or a pairing of a user and a deviceare authorized to access a file 121 or a reference 124 based on accessrights. In one example, access rights are compliance rules that can bedetermined at the time of the access request. The management service 115can provide files 121 and references 124 to authorized client devices106. The management service 115 can also manage and oversee files 121and references 124 stored in data store 112.

The management service 115 can facilitate enrollment of a client device106 on behalf of a user account. In one example, an employer can operatethe management service 115 to ensure that the client devices 106 of itsemployees operate in compliance with the security policies. In anotherexample, an employer can configure the management service 115 to enforcedifferent policies (or no policies at all) based upon which users oremployees are currently logged into or otherwise operating the clientdevice 106. The management service 115 can also facilitate access toemail, calendar data, contact information, and other resources providedby the computing environment 103 or accessible on the client device 106.

According to one example, a client device 106 must have a user accountvalidated by the management service 115 in order to access the files121. The management service 115 can restrict permissions for the clientdevice 106. For example, an employer can grant a first user account readand write access to a file 121, while granting only read access for thefile 121 to a second user account. In this example, the managementservice 115 can authorize the first user account to read and write tothe file 121 while restricting the second user account to only readingthe file 121. The management service 115 can provide the file managementapplication 133 with access to files 121 that are authorized by themanagement service 115 for the user account.

The client device 106 is representative of multiple client devices 106that can be coupled to the network 109. The client device 106 caninclude, for example, a processor-based system such as a computersystem. The computer system can be exemplified in the form of a desktopcomputer, a laptop computer, a personal digital assistant, a mobilephone (e.g., a “smartphone”), a set-top box, a music player, a web pad,a tablet computer system, a game console, an electronic book reader, orany other device with like capability. The client device 106 can includea data store 130, a file management application 133, a renderingapplication 136, and other components. The client device 106 can includea display 139 as well as input devices 142, such as a mouse, touch pad,or touchscreen that facilitates a user input or other types of datainput into the client device 106.

The client device 106 can execute the file management application 133,the rendering application 136, or other components. The file managementapplication 133 can access, manage, edit, or perform other functionswith respect to files, such as files 145, references 148, and otherfiles. As examples, a file 145 can include an image, a video, a wordprocessing document, a spreadsheet, a PDF, an eBook, and other files.The rendering application 136 can present files to a user by generatinga user interface. For example, the rendering application 136 can renderthe files 145 with the corresponding references 148 overlaid orsuperimposed on the rendered file, such as in a user interfacedisplaying the file 145. In addition, the rendering application 136 canfacilitate editing of the contents of a file 145. The renderingapplication 136 can also allow a user to create a reference 148corresponding to a file 145.

The data store 130 can include files 145 and references 148. Accordingto one example, the client device 106 is associated with a user accountauthenticated by the management service 115. The file managementapplication 133 can transmit an authentication credential to themanagement service 115 to authenticate the client device 106. Onceauthenticated, the management service 115 can provide the filemanagement application 133 with access to files 121 and references 124that are associated with a user account corresponding to the clientdevice 106.

The managed devices 120 can include information regarding the clientdevices 106 that are managed and controlled by the management service115. The managed devices 120 for a particular client device 106 caninclude, for example, the identification of a user assigned to theclient device 106, the identification of applications that are installedin the client device 106, historical data regarding the operation of theclient device 106, and other information.

In addition, the managed device 120 for a particular client device 106can include one or more device profiles. A device profile can comprise aset of compliance rules that can be specified by the management service115. The management service 115 can assign various compliance rules to aclient device 106, a user account associated with the client device 106,or to a pairing of the client device 106 and the user account associatedwith the client device 106.

The compliance rules can specify conditions that must be satisfied for aclient device 106 to be deemed compliant with the compliance rule. Inone example, a compliance rule can specify that particular applicationsare prohibited from being installed on a client device 106. In anotherexample, a compliance rule can specify that a lock screen is required tobe generated when the client device 106 is “awoken” from a low power(e.g., “sleep”) state and that a passcode is required for a user tounlock the lock screen. Additionally, some compliance rules can be basedon time, hardware configuration, software configuration, geographicallocation, network properties, or other predefined conditions.

When the compliance rules for a particular device profile are satisfied,the management service 115 can determine that the corresponding clientdevice 106 is compliant with the device policy. For instance, a clientdevice 106 can satisfy a compliance rule when a client device 106 islocated within a particular geographic location. In one example, aclient device 106 can satisfy a compliance rule when the client device106 is in communication with a particular network 109, such as aparticular local area network that is managed by the computingenvironment 103. Furthermore, a compliance rule in another example canbe satisfied upon the time and date matching specified values.

Another example of a compliance rule involves whether a user belongs toa particular group of authorized users. A compliance rule can include awhitelist or a blacklist that specifies whether particular users orgroups of users are authorized users. In various examples, the computingenvironment 103, the client device 106, or a combination of both thecomputing environment 103 and the client device 106 can determinewhether a client device 106 satisfies a compliance rule.

In some examples, a company can operate the management service 115 toensure that the client devices 106 of its users satisfy respectivecompliance rules. By ensuring that the client devices 106 of its usersare operating in compliance with the compliance rules, the company cancontrol access to resources to thereby improve the security of clientdevices 106 associated with the company and the users of the clientdevices 106. The file management application 133 can read and write tofiles 145 and references 148. In one example, the file managementapplication 133 receives files 121 and references 124 from themanagement service 115 and stores the items in files 145 and references148, respectively. The file management application 133 can perform async of files 145 with any files 121 associated with a user accountauthenticated for the client device 106. The file management application133 can also perform a sync of references 148 with any references 124associated with any files 145. The file management application 133 andrendering application 136 can be used to create, access, edit, orperform other functions with respect to a file 145.

According to one example, the management service 115 can restrict thefile management application 133 from transferring a new version of afile 145 to files 121 if the user account is limited to read onlyaccess. In one example, the file management application 133 is stillable to write changes to the file 145 locally on the client device 106when the user account is not authorized for write permissions. Inanother example, the file management application 133 prevents the file145 from being saved if the user account is not authorized to write tothe file 145. The file management application 133 can query themanagement service 115 to determine permissions for the user account.

Multiple versions of a file 121 and 145 can be stored in the data stores112 and 130. According to one example, a single file 121 or 145 storedin data store 112 or 130 can include more than one version of the file121 or 145. In another example, multiple versions of a single file 121or 145 can be stored in data store 112 or 130 as separate entries. Thechanges occurring from one version to the next version of a single file121 or 145 can be stored as a difference from the one version to thenext version. In this example, the multiple versions can be storedcollectively as a single entry in files 121 or 145 including an originalfile and differences between each version.

The files 121 and 145 can include metadata describing versioninginformation for stored files. The metadata can include a list ofversions, a latest version, a current version, authors, last modifieddate, last synced date, a unique identifier, and other properties of thefiles 121 and 145. The unique identifier can be shared between the files121 and 145. In one example, a single file that is stored in both files121 and files 145 has the same unique identifier in both files 121 and145. The unique identifier can also be shared between versions of a file121 and 145. The unique identifier can include a file component and aversion component. For example, two versions of a file 121 or 145 canhave the same file component of the unique identifier, but havedifferent version components. As an example, a first file 121 can have aunique identifier including a file identifier set to 1527 and a versionidentifier set to 1 while an updated version of the file 121 can have aunique identifier including a file identifier set to 1527 and a versionidentifier set to 2.

The files 121 and 145 can include documents in various formats includingMicrosoft Office formats, such as files generated in Word, Excel,PowerPoint, OneNote, Publisher, or Visio; Portable Document Format(PDF); Rich Text Format (RTF); Plain Text Documents (TXT); CommaSeparated Values (CSV); Extensive Markup Language (XML); OpenOfficeformats, such as file formats generate by Writer, Calc, Draw, Impress,Math, and Chart; and other formats. Each reference 124 or 148 can bestored as a Java Script Object Notation (JSON) object, stored asmultiple data fields, or stored in another structure. In one example,the file management application 133 converts multiple stored data fieldsinto a JSON object when loading from the data store 130.

The rendering application 136 can render a user interface on the display139. The rendering application 136 can receive inputs from input device142. The rendering application 136 can also communicate with the filemanagement application 133. In one example, the file managementapplication 133 and the rendering application 136 both have access to aportion of memory of the client device 106. In another example, the filemanagement application 133 and the rendering application 136 communicatethrough a socket connection. In yet another example, the file managementapplication 133 and the rendering application 136 communicate by makingremote procedure calls or other inter-application communicationmechanisms provided by an operating system of the client device 106.

The file management application 133 can transmit a list of files 145 tothe rendering application 136. The rendering application 136 can rendera user interface that includes the list of files 145. In response to auser selection of a file 145, the rendering application 136 can transmita request to the file management application 133 for the selected file145. The file management application 133 can retrieve the stored file145 including any references 148 associated with the file 145 from thedata store 130. As an example, the file management application 133 canquery the data store 130 for the file 145 and references 148 and placethe file 145 and references 148 into local memory.

The file management application 133 can initiate the process of storingan encrypted version of a file 121 or 145, or a reference 124 or 148,for various reasons. For example, in some examples, the file managementapplication 133 can initiate the process in response to a request fromthe user of the client device 106 to “save” the file 145. In anotherexample, the process can be initiated in response to a user of theclient device 106 requesting to “share” the file 145 with another user.In this example, the encrypted file 145 can be transmitted to themanagement service 115 and stored in data store 112 as file 121. Thefile management application 133 can also encrypt any references 148 inthe file 145 and transmit the encrypted references 148 to the managementservice 115. The management service 115 can transmit the encrypted file121 to the other user. In an alternative example, the data store 112 canbe the default storage used by the file management application 133, andthe file management application 133 can initiate the process of storingan encrypted version of the file 121 in the data store 112 automaticallyin response to the file being created or saved.

Upon determining that an encrypted version of a file 121 is to be storedin the data store 112, the client device 106 can begin encrypting thefile 121. In some examples, the encryption key and encryption algorithmused by the client device 106 can be specified by the management service115. In an alternative example, the client device 106 can transmit thefile to the management service 115, and the management service 115 canencrypt the file 121.

The rendering application 136 can receive a request from a user togenerate a reference 148 for a file 145. The request can be a request tocreate an annotation, a bookmark, or other reference 148. In oneexample, a section of text can be highlighted by the user. In anotherexample, a freehand drawing can be received from the user. The freehanddrawing can include points within the file 145. In one example, thepoints are an array of points along a line and the freehand drawing alsoincludes a width of the line and a color of the line.

According to one example, the rendering application 136 can facilitate aselection of whether to apply a reference 148 in future versions of afile 145, such as upon creation of the reference 148. The renderingapplication 136 can store the selection with the reference 148. Therendering application 136 can include or exclude a reference 148 in afuture version of a file 145 in response to the user selection. Uponcreation of a reference 148, the reference 148 can be associated withcompliance rules. The user accounts that are authorized to make changesto current or future file versions can be determined. In one example,the rendering application 136 prompts a user for authorized useraccounts. In another example, the management service 115 determineswhich user accounts are authorized to make changes to current or futurefile versions, such as based on data in managed devices 120.

The rendering application 136 can generate a visual indication of thedata associated with the request. For example, the rendering application136 can highlight text selected to create a reference 148. In anotherexample, the rendering application 136 can generate a line with apredetermined color and thickness on the display connecting pointsreceived from the input device 142. The rendering application 136 cangenerate a user interface to facilitate adding the reference. The userinterface can include user interface elements to receive inputparameters along with the request to add the reference. According to oneexample, when a section of text is selected through the input device142, the rendering application 136 displays the text as highlighted onthe user interface. In this example, the user interface includes a userinterface element to add a reference 148. When a user selects the userinterface element, the rendering application 136 receives the request togenerate the reference 148.

The rendering application 136 can generate a data object for thereference 148 in response to the request to add the reference 148 tofile 145. The data object can include a unique identifier andcharacteristics of the file 145. After the request to generate thereference 148 is received, the rendering application 136 determines thecharacteristics from the file 145 to include within the data object. Thenumber of characteristics that the rendering application 136 determinescan be configurable. In one example, the rendering application 136 candetermine six characteristics. The characteristics can include astarting page and an ending page of the reference 148. Thecharacteristics can also include strings and images located within apredetermined distance of the reference 148 and a location of thestrings and images. In one example, the characteristics include aresolution of an image proximate to the reference 148. Thecharacteristics can also include a section or a subsection within thefile 145 and at least a portion of the name of the section orsubsection.

The rendering application 136 can transmit the data object for thereference 148 to the file management application 133. The filemanagement application 133 can store the data object for the reference148 in data store 130 separate from the file 145. The stored reference148 can correspond to multiple files 145. In one example, when the file145 that a reference 148 was created in is loaded, the file managementapplication 133 also loads the reference 148 and transmits the file 145and reference 148 to the rendering application 136.

According to one example, a pilot creates a reference 148 on a clientdevice 106 in a file 145. In this example, the file 145 includes adetailed flight plan for an upcoming flight, and the reference 148 is anannotation regarding the pre-flight checklist. An airline employeeupdates the detailed flight plan from a remote client device 106 afterthe reference 148 is generated, and the management service 115 transfersthe updated detailed flight plan to the file management application 133.The pilot opens the updated detailed flight plan using the renderingapplication 136. The rendering application 136 transmits a request toopen the updated detailed flight plan to the file management application133. The file management application 133 transmits the updated detailedflight plan and the annotation corresponding to the earlier version ofthe detailed flight plan to the rendering application 136. The renderingapplication 136 determines where to put the annotation in the updateddetailed flight plan based on the characteristics stored with theannotation.

The management service 115 can transfer references 124 to a clientdevice 106 corresponding to a file 145 stored on the client device 106.The file management application 133 can store the references 124 asreferences 148. In one example, the references 148 are third partyreferences that are not associated with a user account corresponding tothe client device 106. The references 148 can be references generated byanother user on another client device 106 in the file 145. In thisexample, the rendering application 136 does not place the references 148in the file 145 when rendering the file 145 for a user. However, otherreferences 148 may be associated with the user account corresponding tothe client device 106. The rendering application 136 can render the file145 including the other references 148 in the file 145, but omitting thereferences 148 not associated with the user account.

The rendering application 136 can generate a prompt to facilitate aselection of references 148. For example, the rendering application 136can generate a user interface including a list of references 148. Theuser interface can include a user interface element corresponding toeach of the references 148 in the list. The user interface elements canfacilitate selection or deselection of the references 148. The renderingapplication 136 can render the file 145 including any selectedreferences 148 overlaid or superimposed on the file 145. The prompt canfacilitate selection of references 148 based on user account. Forexample, a user can select to render the file 145 with references 148created by a first user and an administrative user while omittingreferences 148 created by a second user. In one example, the renderingapplication 136 can store the user selection with the file 145 or thereference 148. In another example, a user selection can be stored as auser preference, such as in managed devices 120.

According to one example, the rendering application 136 limits the listof references 148 included in a prompt to references 148 that werecreated by other users or created on other client devices 106. Therendering application 136 can omit the prompt or omit a reference 148from the list of references 148 if the user account associated with theclient device 106 creates the reference 148. In another example, therendering application 136 can also omit the reference 148 if the useraccount created the reference 148 on another client device 106. In thisexample, the rendering application 136 can render the file 145 includingany references 148 created by a user account associated with the clientdevice 106 and any references 148 selected by the user and created byother user accounts.

The rendering application 136 can select which references 148 to overlayor superimpose on a display of a file 145 based on user preferences. Forexample, the rendering application 136 can include references 148 basedon user preferences without user interaction. The user preferences caninclude a previous indication of whether to include or exclude areference. For example, the rendering application 136 can includereferences 148 that the user previously selected for inclusion. Therendering application 136 can also omit references 148 that the userpreviously selected for exclusion.

The rendering application 136 can include references 148 created byauthorized users. In one example, the authorization of a user can bedetermined by the management service 115. The management service 115 candetermine whether a user account has access rights for a file 121 or145. In another example, the authorized users can include users selectedby a user of the client device 106. For example, a user can select toshare a file 145 with another user account or authorize access to a file145 for another user account.

The rendering application 136 can identify elements of the file 145corresponding to the references 148 not associated with the useraccount. The elements can include a section of text, an image, aheading, or other elements. The rendering application 136 can warn theuser of the client device 106 if the user attempts to edit or delete oneof the elements in the file 145. For example, the rendering application136 can generate a warning informing the user that another user hasgenerated a reference 148 in the file 145. The rendering application 136can require the user to submit a confirmation of the edits or deletionsprior to allowing the user to edit or delete the element.

Turning to FIG. 2, shown is a pictorial diagram of an example userinterface 203 generated by the rendering application 136. The renderingapplication 136 can render a file 145 within the user interface 203. Forexample, the rendering application 136 can render a Plane Mechanics filefor a pilot on a client device 106. A pilot can add references 148 tothe Plane Mechanics file that are saved separate from the file 145. Therendering application 136 can include the references 148, which wasadded in one version of the file 145, in another version of the file145. In one example, the reference 148 was generated in a later versionof the file 145, and the rendering application 136 included thereference 148 when opening an earlier version of the file 145.

The user interface 203 illustrates a file 145 including a subsection209, a text 212, and an image 215. A portion of text 218 can be selectedon the client device 106. For example, if a pilot wants to add areference 148 to text in subsection “2.5 Weight and Balance,” the pilotpresses and holds a finger on the text 212 to initiate selecting of theportion of text 218. The pilot drags the text selection with the fingerto include the portion of text 218 and then releases the finger from thedisplay 139. When the portion of text 218 is selected, the renderingapplication 136 can display several options on the user interface 203,such as an add annotation button 221, an add bookmark button 224, and acancel button 227.

When the add annotation button 221 is selected, the renderingapplication 136 can display a text input field to receive an annotationfor the selected text. The rendering application 136 can display akeyboard on the display for a user to enter text, utilize a physicalkeyboard, use a remote keyboard such as a Bluetooth keyboard, or utilizeanother text entry device. Once the annotation is finalized, therendering application 136 receives a request to add the reference 148.For example, when a pilot finishes adding an annotation, the pilotpresses a “Save” button to finalize the annotation.

When the add bookmark button 224 is selected, the rendering application136 can generate a data object for the bookmark to add the bookmark as areference 148. In one example, the rendering application 136 prompts theuser for a name of the bookmark prior to adding the bookmark. The cancelbutton 227 can be selected to remove the options from the user interface203. In one example, selecting the cancel button 227 also causes therendering application 136 to deselect the portion of text 218.

The rendering application 136 can generate a data object for therequested reference 148. According to one example, when a pilotfinalizes adding an annotation to the portion of text 218, the renderingapplication 136 receives a request to add the annotation from anoperating system on the client device 106. The operating system can makea call to a function of the rendering application 136 in response to aselection of a user interface element. The rendering application 136generates a data object for the annotation including a type field set to“Text,” a descriptor field set to “Note,” a text content field set tothe portion of text 218, search string fields containing samples of thetext 212, image fields containing properties of the image 215, alocation field set to a position of the portion of text 218 relative tothe image 215, a subsection field set to “2.5 Weight and Balance,” astart and end page field, and other characteristics of the file 145.

The rendering application 136 can transmit the data object for thereference 148 to the file management application 133. The filemanagement application 133 can receive the data object and store thedata object as a reference 148 in data store 130. According to oneexample, the file management application 133 also syncs the newlycreated reference 148 with references 124 in the data store 112. In thisexample, the file management application 133 can sync the reference 148by transmitting the reference 148 to the management service 115. In oneexample, the rendering application 136 transmits the data object whenthe data object is generated. In another example, the renderingapplication 136 transmits the data object when the file 145 is saved.

The rendering application 136 can transmit the file 145 and anycorresponding references 148 together to the file management application133 to be saved when a user saves the file 145. The renderingapplication 136 can close the file 145 in response to an indication by auser to close the file. The rendering application 136 can automaticallysave the file 145 and any corresponding references 148 in response tothe indication by the user to close the file.

With reference to FIG. 3, shown is another example of a user interface303 generated by the rendering application 136. The renderingapplication 136 can render a list of files 145 available to be openedusing the user interface 303 on the display 139. According to oneexample, the rendering application 136 displays a “Takeoff Procedure”file 306, a “Landing Equipment” 309 file, and a “Plane Mechanics” file312.

In one example, the rendering application 136 receives a request to opena file 145 from user interface 303. The rendering application 136requests the file 145 from the file management application 133. The filemanagement application 133 retrieves the file 145 from the data store130. The file management application 133 also searches the data store130 for any references 148 corresponding to the file 145. According toone example, a unique identifier is stored for each of the references148 corresponding to the file 145. The unique identifier can be limitedto a file component of a unique identifier for the file 145. Forexample, when a reference 148 is added, the reference 148 can beapplicable to all versions of the file 145 for which the reference 148is being added.

In another example, the file management application 133 processes all ofthe references 148 to determine which of the references 148 areapplicable to the file 145. For example, when a file 145 is retrieved,the file management application 133 can search the file 145 forcharacteristics stored in the reference 148. The file managementapplication 133 can perform this search for each of the references 148to determine which of the references 148 are applicable to the file 145.A reference 148 can be applicable to a file 145 when a minimum thresholdscore is calculated for the reference 148. The file managementapplication 133 can provide the references 148 to the renderingapplication 136, and the rendering application 136 can determine whichof the references 148 are applicable to the file 145.

The user interface 303 can include version information for each of thefiles 145. As one example, the user interface 303 displays that “TakeoffProcedure” file 306 has three versions, the “Landing Equipment” 309 filehas one version, and the “Plane Mechanics” file 312 has two versions. Inthis example, when a pilot selects the “Plane Mechanics” file 312, theuser interface 303 displays multiple user interface element fordifferent options related to the “Plane Mechanics” file 312. The userinterface elements can include an Open Version 1 element 315, an OpenVersion 2 element 318, and a cancel element 321.

According to one example, when a pilot selects Open Version 2 element318, the rendering application 136 transmits a request to open thesecond version of the “Plane Mechanics” file 312 to the file managementapplication 133. The file management application 133 loads the “PlaneMechanics” file 312 from files 145. The file management application 133also loads references 148 corresponding to the “Plane Mechanics” file312. For example, the file management application 133 can searchreferences 148 for a unique identifier corresponding to the “PlaneMechanics” file 312, such as a file component of a unique identifier forthe file 145.

The references 148 corresponding to the “Plane Mechanics” file 312 mayhave been generated in either version one of the “Plane Mechanics” file312 or version two of “Plane Mechanics” file 312. The file managementapplication 133 can transmit the second version of the “Plane Mechanics”file 312 and the references 148 corresponding to the “Plane Mechanics”file 312 to the rendering application 136.

With reference to FIG. 4, shown is another example of a user interface403 generated by the rendering application 136. According to oneexample, the rendering application 136 receives a request to open asecond version of the “Plane Mechanics” file 312. The renderingapplication 136 transmits a request for the second version of the “PlaneMechanics” file 312 to the file management application 133, and receivesthe second version of the “Plane Mechanics” file 312 includingreferences 148 applicable to the “Plane Mechanics” file 312.

The rendering application 136 can determine a placement for thereferences 148 within a file 145, such as the second version of the“Plane Mechanics” file 312, based on a data object associated with eachreference 148. The rendering application 136 can generate and render thefile 145 in user interface 403 including the references 148. The userinterface can include a subsection 406, a text 409, a portion of text412, an annotation 415, and an image 418. The annotation 415 cancorrespond to the portion of text 218.

According to one example, the rendering application 136 receives areference 148 from the file management application 133 for theannotation 415. The reference 148 includes a data object including atype field set to “Text,” a descriptor field set to “Note,” a textcontent field set to “inches. It is to the right of the datum andtherefore the result is a positive value,” a search string set to “thenew arm of weight A,” a search string set to “is 110−50=60 inches,” animage field with properties of the image 215, a location field, asubsection field set to “2.5 Weight and Balance,” a start and end pagefield, and other characteristics of the “Plane Mechanics” file 312.

The rendering application 136 can search the file 145 for the each ofthe characteristics from the reference 148. According to one example,the rendering application 136 searches for the search string of “the newarm of weight A” and determines whether the string is located in text409. The rendering application 136 also searches for search string “is110−50=60” and fails to locate the string because the text was changedin the second version. The rendering application 136 searches for animage with properties similar to image 215 and determines image 418shares similar properties to image 215. The rendering application 136also searches for other characteristics contained in the reference 148.The rendering application 136 determines that the reference 148corresponds to text 412 and adds an annotation 415 when rendering the“Plane Mechanics” file 312 on user interface 403.

When searching an updated version of a file 145, the file 145 caninclude more than one location that matches the characteristics of thereference. According to one example, another user updated the file 145to contain the text “the new arm of weight A” on both page 7 and page23. A reference application 136 can search the file 145 to place areference 148 created for an earlier version of the file 145. In thisexample, a data object for the reference 148 specifies that thereference 148 is located on page 5 and includes a search string of “thenew arm of weight A.” The rendering application 136 can search the file145 for “the new arm of weight A” and find the locations on page 7 andpage 23.

The rendering application 136 can score each of the locations based onthe completeness of matching the data object. The rendering application136 can calculate a higher score for the location on page 7 than for thelocation on page 23 because the location at page 7 is closer to wherethe reference 145 was originally generated. The rendering application136 can also give a greater negative weight for the score of a potentiallocation if the rendering application 136 fails to locate a searchstring field near the location because the text of the file 145 may bemore likely to change than the subsection of a reference 148. Therendering application 136 can give a greater weight to the similarity ofthe text content field to the text in a potential location or to apotential location being within the subsection. The renderingapplication 136 can place the reference 148 at the location having thehighest score.

In some examples, the rendering application 136 can score each page orpotential location in a document 145 for a reference 148 based oncharacteristics of the reference 148. To calculate the score for eachpage or potential location, the rendering application 136 can generate ascore for each characteristic that is found in the document 145. Thescore for the each characteristic can be based on the proximity of apotential location of the characteristic to the original position of thecharacteristic when the reference 148 was created. The renderingapplication can also base the score for a characteristic on theproximity to the other characteristics that are found in the document145. The rendering application 136 can determine the score for each pageor potential location based on a sum or average of the scores for eachcharacteristic that is found on the page or within a configurabledistance to the potential location.

In one example, the score for each page is a floating value between zeroand one, with one being the highest score. When a score for all pages orpotential positions falls below a preconfigured threshold, the renderingapplication 136 can refrain from rendering the reference 148 in thedocument 145. The rendering application 136 can notify a user that thereference 148 is omitted. As an example, the rendering application 136can display a pop-up notification to inform the user that a reference148 was omitted.

With reference to FIG. 5, shown is an example data object 500corresponding to a reference 148. The data object 500 includes areference type 502, a descriptor 504, a text content 506, a subsection509, search strings 512, and image properties 515. The reference type502 can identify a type of a reference 148, such as a “Bookmark,”“Text,” “Highlight,” “Freehand,” “Line,” or other type of reference. Thedescriptor 504 can provide additional information about the reference148 such as “Note,” “Highlight,” “Pen,” or other information. Thedescriptor 504 can be a user entered name or label corresponding to thereference 148.

According to one example, the data object for a reference 148 has thetype set to “Highlight” and the descriptor set to “Highlight.” The dataobject has a highlight data field including a content, an occurrenceindex, a text after highlight, and a position. The rendering application136 can highlight the content within the file 145. The renderingapplication 136 can determine the location of the highlight if more thanone potential location exists by scoring each potential location. Forexample, the rendering application 136 can determine if the textfollowing a potential location matches the text after highlight valueand compare the position of the potential location to the position ofthe highlight.

The occurrence index can be based on the number of times the highlightedtext occurs on a page or within the document 145. The occurrence indexcan be the number of times the highlighted text occurs prior to thehighlighted text plus one for the highlighted text. According to oneexample, the word “airline” is highlighted by a user on page three of adocument 145. In this example, the word “airline” occurs fifteen timeson page three of the document 145, and the fourth occurrence is selectedby the user for highlight. The occurrence index can be set to four toindicate that the fourth occurrence of the word “airline.”

According to one example, a data object for a reference 148 has the typeset to “Line” and the descriptor is set to “Pen.” The data objectincludes line data field including a line color, a line width, a pathcontaining multiple coordinates within the file 145, for example (x, y)coordinates, and other data. The rendering application 136 can draw aline within the file 145 based on the data object. The renderingapplication 136 can draw the line with the color and width specified inthe data object. The rendering application 136 can draw the line througheach of the multiple coordinates specified in the data object.

When a new version of a file 145 is received, components of a dataobject for a reference 148 can be incorrect. The rendering application136 can generate a completeness score for each partially matchinglocation. The rendering application 136 can select the locationcorresponding to the highest score to place the reference 148.

Referring next to FIG. 6, shown is a flowchart that provides one exampleof the operation of a portion of the file management application 133 andthe rendering application 136. As an alternative, the flowchart of FIG.6 may be viewed as depicting an example of elements of a methodimplemented in the client device 106. FIG. 6 illustrates an example ofhow the file management application 133 and the rendering application136 can generate a reference 148 for a file 145 when a user submits arequest to add the reference 148 on the client device 106 using theinput device 142.

At step 603, the rendering application 136 receives a request togenerate a reference 148. The request to generate the reference 148 canbe initiated in response to a selection of a user interface elementusing input device 142. The input device 142 can be overlaid ontodisplay 139. As an example, a pilot can select a user interface on atouch screen device on the display 139 of the client device 106 torequest the rendering application 136 to generate a reference 148. Thepilot may enter details about the reference 148 prior to requesting toadd the reference 148.

At step 606, the rendering application 136 determines characteristics ofthe file 145 near the reference 148. The rendering application 136 cansearch for text and images preceding and following the location at whichthe reference 148 is being generated. The rendering application 136 candetermine characteristics of the text and images preceding and followingthe location. In one example, the rendering application 136 identifiesan image after the requested reference 148 and determines an absoluteposition of the image, a position of the image relative to reference148, a resolution of the image, a width of the image, and a height ofthe image.

At step 609, the rendering application 136 generates a data objectincluding the characteristics. For example, the rendering application136 can store properties of an image in the data object, such as theabsolute position of the image, a position of the image relative toreference 148, a resolution of the image, a width of the image, and aheight of the image. The data object can be in a JSON object. Accordingto one example, the data object formatted according to the format shownfor the data object 500 in FIG. 5. The characteristics can include astarting page and an ending page of the reference 148. The renderingapplication 136 can transmit the generated data object to the filemanagement application 133.

At step 612, the file management application 133 can store the dataobject. For example, the file management application 133 can store thedata object in the data store 130 as a reference 148. In one example,the data object is stored in the data store 130 as a JSON object. Inanother example, the file management application 133 extracts the datafrom the data object and stores the extracted data in the data store130. The file management application 133 can transfer the createdreference 148 to the management service 115. In one example, the filemanagement application 133 sends a message to the management service 115indicating a file 145 or a reference 148 is ready to be transferred, andthe management service 115 pulls the file 145 or the reference 148. Themanagement service 115 can store the received reference 148 in datastore 112 as a reference 124.

Referring next to FIG. 7, shown is a flowchart that provides one exampleof the operation of a portion of the file management application 133 andthe rendering application 136. As an alternative, the flowchart of FIG.7 can be viewed as depicting an example of elements of a methodimplemented in the client device 106. FIG. 6 illustrates an example ofhow the file management application 133 and the rendering application136 can open a file 145 including references 148 corresponding to thefile 145 when a user submits a request to open the file 145 on theclient device 106 using the input device 142.

Beginning at step 703, the rendering application 136 receives a requestto open a file 145. The request to open the file 145 can be initiated inresponse to a selection of the user interface element using input device142, for example, the Open Version 1 element 315 or the Open Version 2element 318 on the user interface 303. As an example, a pilot can selecta user interface on a touch screen device on the display 139 of theclient device 106 to request to open a file 145. The request can includea unique identifier for the file 145. The request can also include aversion number of the file 145. According to one example, the file 145was previously generated on the client device 106. In another example,the file 145 was previously generated elsewhere and received by the filemanagement application 133 from the management service 115. Therendering application 136 can transmit a request to the file managementapplication 133 for the file 145 including a unique identifiercorresponding to the file 145.

At step 706, the file management application 133 identifies references148 in data store 130 corresponding to the file 145. As an example, thefile management application 133 can search the data store for references148 having a unique identifier corresponding to the file 145. In anotherexample, the file management application 133 loads the file 145. In thisexample, the file management application 133 retrieves characteristicsfrom the data store 130 for each reference 148 and determines if thefile 145 matches the characteristics. The file management application133 can identify any references 148 having characteristics that matchthe file 145 as corresponding to the file 145. The file managementapplication 133 can transmit the file 145 and any correspondingreferences 148 to the rendering application 136.

At step 709, the rendering application 136 can determine a position inthe file 145 for each of the references 148. The rendering application136 can receive the file 145 and any corresponding references 148 fromthe file management application 133. The rendering application 136 caniterate through each of the corresponding references 148 to determine aposition in the file 145 for each reference 148. For example, therendering application 136 can determine a position in the file 145matching characteristics described in a data object corresponding to thereference 148.

At step 712, the rendering application 136 can render the file 145including the references 148. For example, the rendering application 136can generate the file 145 with references 148 placed at positionsobtained in step 709. The rendering application 136 can render thegenerated file 145 including the references 148 on the display 139.According to one example, the rendering application 136 identifies afile format for the file 145 and loads a third party librarycorresponding to the file format to render the file 145.

The flowcharts of FIGS. 5 and 6 show an example of the functionality andoperation of implementations of components described herein. Thecomponents described herein can be embodied in hardware, software, or acombination of hardware and software. If embodied in software, eachelement can represent a module of code or a portion of code thatincludes program instructions to implement the specified logicalfunction(s). The program instructions can be embodied in the form ofsource code that includes human-readable statements written in aprogramming language or machine code that includes machine instructionsrecognizable by a suitable execution system, such as a processor in acomputer system or other system. If embodied in hardware, each elementcan represent a circuit or a number of interconnected circuits thatimplement the specified logical function(s).

Although the flowcharts of FIGS. 5 and 6 show a specific order ofexecution, it is understood that the order of execution can differ fromthat which is shown. The order of execution of two or more elements canbe switched relative to the order shown. Also, two or more elementsshown in succession can be executed concurrently or with partialconcurrence. Further, in some examples, one or more of the elementsshown in the flowcharts can be skipped or omitted. In addition, anynumber of counters, state variables, warning semaphores, or messagescould be added to the logical flow described herein, for purposes ofenhanced utility, accounting, performance measurement, ortroubleshooting aid. It is understood that all of these variations arewithin the scope of the present disclosure.

The computing environment 103, the client devices 106, or othercomponents described herein, can each include at least one processingcircuit. The processing circuit can include one or more processors andone or more storage devices that are coupled to a local interface. Thelocal interface can include a data bus with an accompanyingaddress/control bus or any other suitable bus structure. The one or morestorage devices for a processing circuit can store data or componentsthat are executable by the one or processors of the processing circuit.Also, a data store can be stored in the one or more storage devices.

The management service 115, the file management application 133, therendering application 136, and other components described herein can beembodied in the form of hardware, as software components that areexecutable by hardware, or as a combination of software and hardware. Ifembodied as hardware, the components described herein can be implementedas a circuit or state machine that employs any suitable hardwaretechnology. The hardware technology can include one or moremicroprocessors, discrete logic circuits having logic gates forimplementing various logic functions upon an application of one or moredata signals, application specific integrated circuits (ASICs) havingappropriate logic gates, programmable logic devices (e.g.,field-programmable gate array (FPGAs), and complex programmable logicdevices (CPLDs)).

Also, one or more or more of the components described herein thatincludes software or program instructions can be embodied in anynon-transitory computer-readable medium for use by or in connection withan instruction execution system such as a processor in a computer systemor other system. The computer-readable medium can contain, store, ormaintain the software or program instructions for use by or inconnection with the instruction execution system.

The computer-readable medium can include physical media, such as,magnetic, optical, semiconductor, or other suitable media. Examples of asuitable computer-readable media include, but are not limited to,solid-state drives, magnetic drives, flash memory. Further, any logic orcomponent described herein can be implemented and structured in avariety of ways. One or more components described can be implemented asmodules or components of a single application. Further, one or morecomponents described herein can be executed in one computing device orby using multiple computing devices.

It is emphasized that the above-described examples of the presentdisclosure are merely examples of implementations to set forth for aclear understanding of the principles of the disclosure. Many variationsand modifications can be made to the above-described examples withoutdeparting substantially from the spirit and principles of thedisclosure. All of these modifications and variations are intended to beincluded herein within the scope of this disclosure.

Therefore, the following is claimed:
 1. A method for file referencing,comprising: receiving a first request to generate a drawing in a firstversion of a file; generating a first data object corresponding to thedrawing, the first data object comprising at least one characteristic ofthe first version of the file near the drawing, wherein the at least onecharacteristic comprises a location of the drawing with respect to animage location for a respective image and an image characteristic forthe respective image; generating a second data object for a reference;storing the first data object and the second data object separate fromthe file; receiving a second request to open a second version of thefile that is different from the first version of the file; receiving auser selection of the drawing from a list of references to display;determining a position in the second version of the file to place thedrawing based at least in part on the first data object comprising thelocation of the drawing with respect to the image location for therespective image and the image characteristic for the respective image;and rendering the second version of the file including the drawing atthe position, wherein rendering the file comprises omitting a display ofthe reference for the second data object based on the user selection. 2.The method of claim 1, wherein rendering the file including the drawingat the position comprises overlaying the drawing onto the file.
 3. Themethod of claim 1, wherein the first data object comprises an array ofpoints along a line corresponding to the drawing.
 4. The method of claim1, further comprising receiving an indication of a width and a color ofa line for the drawing, wherein the first data object comprises thewidth and the color.
 5. The method of claim 1, wherein the drawingcomprises a freehand drawing.
 6. The method of claim 1, furthercomprising receiving a selection of a particular version of the filefrom among a plurality of versions of the file, wherein the position inthe file is determined for the particular version of the file and thedrawing was generated for a different version of the file.
 7. The methodof claim 1, further comprising, in response to receiving the secondrequest to open the second version of the file, retrieving the firstdata object based in part on a unique identifier corresponding to thefile, and the unique identifier comprises a file identifier componentand a version identifier component.
 8. The method of claim 1, whereindetermining the position in the file to place the drawing comprises:determining a number of potential positions to place the drawing; inresponse to the number of potential positions being one position,determining the one position as the position in the file to place thedrawing; and in response to the number of potential positions being aplurality of potential positions: generating a plurality of scoresindividually corresponding to the plurality of potential positions basedat least in part on the first data object; and determining one of theplurality of potential positions as the position in the file to placethe drawing based at least in part on the plurality of scores.
 9. Anon-transitory computer-readable medium embodying a program for filereferencing that, when executed by a client computing device, causes theclient computing device to at least: receive a first request to generatea drawing in a first version of a file; generate a first data objectcorresponding to the drawing, the first data object comprising at leastone characteristic of the first version of the file near the drawing,wherein the at least one characteristic comprises a location of thedrawing with respect to an image location for a respective image and animage characteristic for the respective image; generate a second dataobject for a reference; store the first data object and the second dataobject separate from the file; receive a second request to open a secondversion of the file that is different from the first version of thefile; receive a user selection of the drawing from a list of referencesto display; determine a position in the second version of the file toplace the drawing based at least in part on the first data objectcomprising the location of the drawing with respect to the imagelocation for the respective image and the image characteristic for therespective image; and render the second version of the file includingthe drawing at the position, wherein rendering the file comprisesomitting a display of the reference for the second data object based onthe user selection.
 10. The non-transitory computer-readable medium ofclaim 9, wherein the first data object comprises an array of pointsalong a line corresponding to the drawing.
 11. The non-transitorycomputer-readable medium of claim 9, wherein the program further causesthe client computing device to at least receive an indication of a widthand a color of a line for the drawing, wherein the first data objectcomprises the width and the color.
 12. The non-transitorycomputer-readable medium of claim 9, wherein the program further causesthe client computing device to at least receive a selection of aparticular version of the file from among a plurality of versions of thefile, wherein the position in the file is determined for the particularversion of the file and the drawing was generated for a differentversion of the file.
 13. The non-transitory computer-readable medium ofclaim 9, wherein program further causes the client computing device toat least retrieve the first data object based in part on a uniqueidentifier corresponding to the file responsive to the second request toopen the second version of the file being received.
 14. Thenon-transitory computer-readable medium of claim 9, wherein the programfurther causes the client computing device to at least: determine anumber of potential positions to place the drawing; in response to thenumber of potential positions being one position, determine the oneposition as the position in the file to place the drawing; and inresponse to the number of potential positions being a plurality ofpotential positions: generate a plurality of scores individuallycorresponding to the plurality of potential positions based at least inpart on the first data object; and determine one of the plurality ofpotential positions as the position in the file to place the drawingbased at least in part on the plurality of scores.
 15. A system for filereferencing, comprising: a data store that comprises machineinstructions; and a computing device in communication with the datastore, wherein the computing device comprises a processor, and themachine instructions, when executed, cause the processor to at least:receive a first request to generate a drawing in a first version of afile; generate a first data object corresponding to the drawing, thefirst data object comprising a location of the drawing with respect toan image location for a respective image and an image characteristic forthe respective image; generate a second data object for a referencebased on a second request; store the first data object and the seconddata object separate from the file; receive a second request to open asecond version of the file that is different from the first version ofthe file; receive a user selection from a list of references to display;determine a position in the second version of the file to place thedrawing based at least in part on the first data object comprising thelocation of the drawing with respect to the image location for therespective image and the image characteristic for the respective image;and render the second version of the file including the drawing at theposition, wherein rendering the file comprises omitting a display of thereference based on the user selection.
 16. The system of claim 15,wherein the machine instructions further cause the processor to at leastreceive a selection of a particular version of the file from among aplurality of versions of the file, wherein the position in the file isdetermined for the particular version of the file and the drawing wasgenerated for a different version of the file.
 17. The system of claim15, wherein the machine instructions further cause the processor to atleast retrieve the first data object based in part on a uniqueidentifier corresponding to the file responsive to the second request toopen the second version of the file being received.
 18. The system ofclaim 15, wherein the machine instructions further cause the processorto at least: determine a number of potential positions to place thedrawing; in response to the number of potential positions being oneposition, determine the one position as the position in the file toplace the drawing; and in response to the number of potential positionsbeing a plurality of potential positions: generate a plurality of scoresindividually corresponding to the plurality of potential positions basedat least in part on the first data object; and determine one of theplurality of potential positions as the position in the file to placethe drawing based at least in part on the plurality of scores.
 19. Thesystem of claim 15, wherein rendering the file further comprisesomitting a display of at least one of an administrator reference or athird reference associated with a second user account.
 20. The system ofclaim 15, wherein the user selection is received based on retrievinguser preferences associated with a user account.